Release 10.1A: OpenEdge Development:
ADM Reference

callstring.p

The callstring.p procedure allows you to make a dynamics call by providing a minimal list of information. The procedure then evaluates the data needed to make the call and performs all the steps necessary to invoke the call. This is advantageous because callstring.p can be run from a client procedure in a single AppServer request.

The caller can invoke procedures and functions in a remote manager by providing mnemonics that are evaluated by the callstring.p on the server. These mnemonics map to handles to procedures that are not known to the client.

The procedure invokes calls using a string containing the parameters in the form:

mode datatype parameter, mode datatype parameter,…

Each token in a group is separated by a space, and when the value of a parameter token is a constant, the value is enclosed in single quotes.

Note: The following examples illustrate code for use in a dynamics environment because they use the Connection Manager.

This code example illustrates a valid callstring.p invocation:

RUN callstring.p ("disconnectService", /* call to make */ "ConnectionManager", /* manager to use */ "INPUT CHARACTER 'sports2000'"). /* parameter string */

The call results in a call to the disconnectService procedure in the Connection Manager in the local session and passes a single input parameter of data type character with the constant value of sports2000.

If the value of the parameter is determined from context, the constant value sports2000 can be replaced with a context variable name:

RUN callstring.p ("disconnectService", /* call to make */ "ConnectionManager", /* manager to use */ "INPUT CHARACTER cDBName"). /* parameter string */

In this sample, cDBName is the name of a property or parameter that was previously set using setPropertyList or setSessionParam.